Skip to main content

DataSource Items

The Items property is used to define and manage manually added static elements in the object when the list is not populated from a data source.

Items

The Items property defines the list of elements displayed in the object.
It is used when the object should show manually defined (static) items instead of dynamically loaded records from a data source.

Through this property, you can add, remove, or edit list elements that will appear within the control during form execution.

When the user clicks on the Items field in the properties panel, the Item Management window opens, allowing configuration of new or existing items.

How It Works

  1. Click the Items field to open the element editing window.
  2. Use the Add button to create new elements.
  3. Define the necessary properties (Key, Text, Title, Icon, etc.) for each element.
  4. Save the configuration — the items will be displayed statically in the object.

Item Properties

PropertyDescription
KeyDefines the unique key value for the item. Each key must be unique within the object. If a duplicate value is entered, the item cannot be added.
TextDefines the text (name) displayed for the item in the user interface.
TitleSpecifies the tooltip text shown when hovering the mouse pointer over the item.
IconIf the item should have an icon, one can be selected from this field.
ItemsAllows adding child items under the current item. Clicking the three dots opens another item configuration window where sub-elements can be added similarly to the parent item. These sub-items are saved under their parent once confirmed.

Example Scenario

Use CaseDescription
Static Dropdown ListDefine options manually (e.g., “Low”, “Medium”, “High”) that are not tied to a data source.
Menu with Sub-itemsCreate a menu structure where parent items contain nested child items for hierarchical representation.
Iconic Item ListDisplay items with meaningful icons for better user experience (e.g., file types, statuses).

Notes

  • Each item key must be unique to prevent conflicts.
  • Nested (child) items can be created under any item to build multi-level structures.
  • The Items property applies only to statically defined data and does not affect items loaded dynamically from an external source.
  • To switch to dynamic population, use properties like Data Source or Binding Configuration instead.